ENUM Queries

You can use Call Setup rules to query an ENUM server and to handle responses from ENUM server. ENUM translates ordinary telephone numbers (E.164 telephone numbers) into Internet addresses (SIP URIs), using the ENUM's DNS NAPTR records. Once resolved into a URI, the device can replace the telephone number in the Request-URI of the SIP message with the URI. When configuring Call Setup rules for ENUM queries, configure the 'Request Type' parameter to ENUM.

Syntax:

■

Result (i.e., URI) of the ENUM query:

enum.result.url.<x>

Where x is optional and can be any of the following:

●

type

●

host

●

mhost

●

userphone

●

looseroute

●

bnce

●

cause

●

user

●

transport-type

●

ac-int

●

param

■

If ENUM query succeeded or not:

enum.found exists
enum.found !exists

Applicable table:

■

Call Setup Rules table:

●

'Condition'

●

'Action Subject' (only enum.result.url)

●

'Action Value' (only enum.result.url)

Example:

ENUM Query Example

Request Type	Request Key	Condition	Action Subject	Action Type	Action Value	Description
ENUM	param.call.dst.user	enum.found exists	header.request-uri.url	Modify	enum.result.url	Performs an ENUM query using the called number and if successful, replaces the entire SIP Request-URI with the retrieved URI.
ENUM	param.call.dst.user	enum.found exists	header.request-uri.url.user	Modify	enum.result.url.user	Performs an ENUM query using the called number and if successful, replaces SIP Request-URI user part with the retrieved URI user part